I ran 'snapcraft --debug'. The build failed. The execution returned to the shell inside the container, with a huge amount of noise, which consists namely of the failed build's normal output except that newline characters are replaced by the literal string '\n', right before the end of execution. The scrollback, as catpured inside Tmux with its capture-pane command, is attached. Note how the noise begins at line 65798 and ends thousands of lines later, at line number 89571. The default configuration of many terminal emulators won't even save that many lines in memory. As such, to the "debug the failed build" problem Snapcraft prepends a new one, namely the problem of figuring out where the failed build's output is even located. It is just a disheartening sight. Sure, right at the end of the execution, it tells us that the execution log is at /tmp/snapcraft.log, which is no real solace considering that inside the container there is no text editor, not even 'cat' or 'less'. Presumably because --debug was used, the log is not saved in the host's filesystem under ~/.local/state/snapcraft/ either. Expected behavior: Build output at most couple of lines above the end of execution, instead of thousands of lines above the end of execution.